Just had a discussion with @sfmskywalker regarding the difference between this package and the way this has been incorporated in netcore 3.1 (https://docs.microsoft.com/en-us/aspnet/core/fundamentals/configuration/options?view=aspnetcore-3.1#options-validation).

The main difference is that the MS provided version does the validation at resolve-time. This package on the other hand, does validation during application startup, not allowing for the application to boot at all if it has been misconfigured. You can achieve this with the built-in MS solution, but you'll need a lot more boilerplate (build a serviceprovider, then try to resolve it as a required service). This is also more error-prone, because you need to remember to resolve every service that you want startup time validation on. In my opinion, this package/change does have its merits, and I'd like to make use of the ConfigureWithValidation(Action<T>) syntax.